Method of managing virtual volumes in a utility storage server system

ABSTRACT

A method is provided to allow a system administrator of a utility storage server to provision virtual volumes several times larger than the amount of physical storage within the storage server. A virtual volume is a virtual representation of multiple disks as a single large volume to a host or an application. In one embodiment, a virtual volume comprises an exception list containing the set of differences from dummy base volume consisting of all zeros. This exception list can be made up of address tables that map virtual volume pages to logical disk pages. As storage demand grows, additional storage is allocated for the address tables and the data pages from separate pools of storage. If any of the pools runs low, more logical disk regions are allocated to that pool.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.60/470,018, filed May 12, 2003, and incorporated herein by thisreference.

FIELD OF INVENTION

This invention relates to a utility storage server and more particularlyto virtual volume management of the utility storage server.

DESCRIPTION OF RELATED ART

A utility storage server may be defined as any carrier-class storagesystem that provisions physical storage to multiple users and/orapplications. To meet the demands of multiple users and applications, asystem administrator has to purchase enough physical storage for theusers and the applications. Often the purchased physical storage isunderutilized as the users and the applications generally fill theirprovisioned storage over time. Thus, what is needed is a method thatallows the system administrator to increase asset utilization and deferexpenses spent on the physical storage.

SUMMARY

In one embodiment of the invention, a method is provided to allow asystem administrator of a utility storage server to provision virtualvolumes several times larger than the amount of physical storage withinthe storage server. A virtual volume is a virtual representation ofmultiple disks as a single large volume to a host or an application. Inone embodiment, a virtual volume comprises an exception list containingthe set of differences from a dummy base volume consisting of all zeros.This exception list can be made up of address tables that map virtualvolume pages to logical disk pages. As storage demand grows, additionalstorage is allocated for the address tables and the data pages fromseparate pools of storage. If any of the pools runs low, more logicaldisk regions are allocated to that pool.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a software architecture of a utility storage serverin one embodiment of the invention.

FIG. 2 illustrates a representation of the mapping of pages in a virtualvolume pages to pages in a logical disk of a node in one embodiment.

FIG. 3 illustrates the mapping of logical disk regions to physical disksin one embodiment of the invention.

FIG. 3A illustrates a virtual volume block address and its componentsegments in one embodiment of the invention.

FIGS. 4A, 4B, and 4C illustrate a method for a virtual volume layer torespond to a write request to the virtual volume in one embodiment ofthe invention.

FIG. 5 illustrates a method for a system manager to respond to an eventrequesting an additional logical disk region from the virtual volumelayer in one embodiment of the invention.

FIG. 6 illustrates a method for the virtual volume layer and the logicaldisk layer to respond to a read request from the host in one embodiment.

DETAILED DESCRIPTION

For a description of a utility storage server, please see U.S. Pat. No.6,658,478, entitled “Data Storage System,” and U.S. patent applicationSer. No. 09/883,681, entitled “Node Controller for a Data StorageSystem,” which are incorporated by reference in their entirety.

FIG. 1 illustrates a software architecture of a utility storage server100 in one embodiment. For simplicity, utility storage server 100 isshown to include a cluster of nodes 102-1 and 102-2 although the clustermay include additional nodes.

Node 102-1 includes a system manager 104 residing in the user levelabove the operating system and a data stack 106-1 residing in the kernellevel of the operating system. Data stack 106-1 includes a target driver108-1, a virtual volume layer 110-1, a logical disk layer 112-1, aphysical disk layer 114-1, and an initiator driver 116-1.

Initiator driver 116-2 performs the actual reads and writes to thephysical disk drive using, e.g., the SCSI protocol. Physical disk layer114-1 routes the read and write requests to the appropriate node withaccess to the physical disk drives on disk chassis 120.

Logical disk layer 112-1 organizes “chunklets” of physical disks 202-1to 202-i (FIG. 3) into logical disks (LDs) of specific RAID levels. Inone embodiment, a chunklet is 256 megabytes of contiguous disk space.System manager 104 allocates logical disk storage space, in units oflogical disk regions (shown as a stripe through chunklets 204-1 to 204-ifrom physical disks 202-1 to 202-i in FIG. 3), to virtual volume layer110-1. In one embodiment, an LD region is 256 megabytes of logical diskstorage space. Virtual volume layer 110-1 divides up each LD region intopages for storing data. In one embodiment, a page has a size of 16kilobytes and holds thirty-two 512 byte data blocks. Virtual volumelayer 110-1 maps pages in a virtual volume to pages in the logical diskand sends the read/write requests to the proper logical disk addresseswithin logical disk layer 112-1.

Target driver 108-1 communicates the read and write requests to virtualvolume layer 11-1. A host 118 sends read and write requests to thevirtual volume via target driver 108-1 using, e.g., the SCSI protocol.

Similarly, node 102-2 includes a data stack 106-2 residing in the kernellevel. Data stack 106-2 also includes a target driver 108-2, a virtualvolume layer 110-2, a logical disk layer 112-2, a physical disk layer114-2, and an initiator driver 116-2. Components of data stacks 106-1and 106-2 communicate by a node-to-node link 122.

System manager 104 resides only on one of the nodes of utility storageserver 100. If system manager 104 fails at one of the nodes, it can berestarted at another node. System manager 104 keeps a single systemimage of utility storage server 100. System manager 104 also servicesevents from the data stacks, delivers configuration commands to the datastacks, and records system configuration information in a table ofcontents (TOC) on a physical disk drive.

FIG. 2 illustrates the mapping of a virtual volume 208 to a logical disk(e.g., logical disk 207 in FIG. 3) in one embodiment of the invention.Virtual volume 208 is an exception list made up of address tables thatmap pages of a virtual volume 208 to pages of logical disk 207 storage.Virtual volume 208 also includes pools 412 and 414 of logical diskstorage from which these exception list tables and logical disk datapages are allocated. In one embodiment, virtual volume 208 isimplemented using a snapshot mechanism in which the exception listtracks changes to a dummy base volume consisting of only zeroes.

The address tables are divided into three levels. This is becausevirtual volume 208 is written or read in blocks each identified by avirtual volume block address. The virtual volume block address includesa virtual volume page address consisting of parts 450, 460, and 470(FIG. 3A). Parts 450, 460, and 470 lead to a page in virtual volume 208,which is mapped to a corresponding page in logical disk 207. The virtualvolume block address further includes a block offset 480 (FIG. 3A) thatleads to a data block in the corresponding page in logical disk 207.

A level 1 table (e.g., table 402) consists of entries that can beindexed by the first part 450 of the page address. Specifically, part450 provides an offset from the start of the level 1 table. Each entryin the level 1 table stores a pointer to the start of a level 2 tablethat shares the first part of the page address.

Each of the level 2 tables (e.g., table 404-0 to 404-31) consists ofentries that can be indexed by the second part 460 of the pageaddresses. Specifically, part 460 provides an offset from the start of alevel 2 table. Each entry in the level 2 table stores a pointer to thestart of a level 3 table that shares the first and the second part ofthe page address.

Each of the level 3 tables (e.g., tables 406-0 to 406-2047 in oneembodiment) consists of entries that can be indexed by the third part470 of the page addresses. Specifically, part 470 provides an offsetfrom the start of a level 3 table. Each entry in the level 3 tablestores a pointer to a page in a logical disk. Accordingly, a page in thevirtual volume (e.g., VV data page) is mapped to a page in a logicaldisk (e.g., LD data page). Part 480 of the page address identifies anoffset of a data block (i.e., block offset) from the start of the LDdata page.

Virtual volume layer 110-1 initially creates virtual volume 208 withonly a blank level 1 table. As data is written to virtual volume 208(described later), virtual volume layer 110-1 allocates LD data pagesand adds the level 2 and level 3 tables that are necessary to managethese LD data pages.

FIGS. 4A, 4B, and 4C illustrate a method 300 for virtual volume layer110-1 to respond to a write request from host 118 (or an application) tovirtual volume 208 in one embodiment.

In step 302, virtual volume layer 110-1 receives a write request to adata block in virtual volume 208. The write request identifies the datablock by the ID of virtual volume 208 and its virtual volume blockaddress. Step 302 is followed by step 304.

In step 304, virtual volume layer 110-1 traverses tables 402, 404, and406 to find the LD data page that corresponds to the virtual volumeblock address. Step 304 is followed by step 306.

In step 306, virtual volume layer 110-1 determines if the correspondingLD data page has been found. If so, step 306 is followed by step 308.Otherwise step 306 is followed by step 312. The corresponding LD datapage cannot be found if the VV data page to-be-written in virtual volume208 has not been mapped to an LD data page by pointers and addresstables as described above.

In step 308, virtual volume layer 110-1 instructs logical disk layer112-1 to issue a write to the corresponding LD data page. Specifically,virtual volume 110-1 identifies the block by a logical disk ID and anoffset from the start of the logical disk. The offset from the start ofthe logical disk is determined from the sum of (1) the offset of the LDregion from the start of the logical disk, (2) the offset of the LD datapage from the start of the LD region, and (3) the block offset of thedata block from the start of the LD data page. In one embodiment, thewrite is replicated to the other nodes (e.g., node 102-2) for failoverprotection. Step 308 is followed by step 310.

In step 310, virtual volume layer 110-1 returns a “pass” status to thehost and ends method 300.

In step 312, virtual volume layer 110-1 determines if a level 2 (L2)address table exists for the requested VV data page. If so, then step312 is followed by step 326. Otherwise step 312 is followed by step 314.

In step 314, virtual volume layer 110-1 determines if the number ofavailable LD table pages in a pool 412 (FIG. 2) for storing addresstables is less than a threshold. If so, then step 314 is followed bystep 316. Otherwise step 314 is followed by step 322.

In step 316, virtual volume layer 110-1 issues an event to systemmanager 104. In response to the event, system manager 104 may allocatean available LD region to virtual volume layer 110-1. System manager 104may allocate the LD region in a method 500 described later in referenceto FIG. 5. Virtual volume layer 110-1 divides the allocated LD regioninto LD table pages and increments pool 412 with these new pages. Step316 is followed by step 318.

In step 318, virtual volume layer 110-1 determines if an LD table pageis available to be used as an L2 table. If so, then step 318 is followedby step 322. Otherwise step 318 is followed by step 319A.

In step 319A, virtual volume layer 110-1 sleeps for a predeterminedamount of time. Step 319A is followed by step 319B.

In step 319B, virtual volume 110-1 determines if a timeout has beenreached. If so, then step 319B is followed by step 320. Otherwise step319B is followed by step 318.

In step 320, virtual volume 110-1 returns a “fail” status to the hostand ends method 300.

In step 322, virtual volume 110-1 creates an L2 table from an availableLD table page in pool 412. Step 322 is followed by step 324.

In step 324, virtual volume 110-1 updates the level one (L1) table witha pointer to the newly created L2 table. Specifically, virtual volume110-1 writes the pointer in the L1 table entry having an offsetidentified by the first part of the virtual volume page address. Step324 is followed by step 326.

In step 326 (FIG. 4B), virtual volume layer 110-1 determines if a level3 (L3) table exists for the requested VV data page. If so, then step 326is followed by step 340. Otherwise step 326 is followed by step 328.

In step 328, virtual volume layer 110-1 determines if the number ofavailable LD table pages in pool 412 (FIG. 2) for storing address tablesis less than a threshold. If so, then step 328 is followed by step 330.Otherwise step 328 is followed by step 336.

In step 330, virtual volume layer 110-1 issues an event to systemmanager 104. In response to the event, system manager 104 may allocatean available LD region to virtual volume layer 110-1. System manager 104may allocate the LD region in a method 500 described later in referenceto FIG. 5. Virtual volume layer 110-1 divides the LD region into LDtable pages and increments pool 412 with these new pages. Step 330 isfollowed by step 332.

In step 332, virtual volume layer 110-1 determines if an LD table pageis available to be used as an L3 table. If so, then step 332 is followedby step 336. Otherwise step 332 is followed by step 333A.

In step 333A, virtual volume layer 110-1 sleeps for a predeterminedamount of time. Step 333A is followed by step 333B.

In step 333B, virtual volume 110-1 determines if a timeout has beenreached. If so, then step 333B is followed by step 334. Otherwise step333B is followed by step 332.

In step 334, virtual volume 110-1 returns a “fail” status to the hostand ends method 300.

In step 336, virtual volume 110-1 creates an L3 table from an availablepage in pool 412. Step 336 is followed by step 338.

In step 338, virtual volume 110-1 updates the corresponding L2 tablewith a pointer to the newly created L3 table. Specifically, virtualvolume 110-1 writes the pointer in the L2 table entry having an offsetidentified by the second part of the virtual volume page address. Step338 is followed by step 340.

In step 340 (FIG. 4C), virtual volume layer 110-1 determines if an LDdata page in the logical disk exists for the virtual volume blockaddress received. If so, then step 340 is followed by step 352.Otherwise step 340 is followed by step 342.

In step 342, virtual volume layer 110-1 determines if the number ofavailable LD data pages in a pool 414 (FIG. 2) for storing data is lessthan a threshold. If so, then step 342 is followed by step 344.Otherwise step 342 is followed by step 350.

In step 344, virtual volume layer 110-1 issues an event to systemmanager 104. In response to the event, system manager 104 may allocatean available LD region to pool 414. System manager 104 may allocate theLD region in method 500 described later in reference to FIG. 5. Virtualvolume layer 110-1 divides the LD region into LD data pages andincrements pool 414 with these new pages. Step 344 is followed by step346.

In step 346, virtual volume layer 110-1 determines if an LD data page isavailable to be used. If so, then step 346 is followed by step 350.Otherwise step 346 is followed by step 347A.

In step 347A, virtual volume layer 110-1 sleeps for a predeterminedamount of time. Step 347A is followed by step 347B.

In step 347B, virtual volume layer 110-1 determines if a timeout hasbeen reached. If so, then step 347B is followed by step 348. Otherwisestep 347B is followed by step 346.

In step 348, virtual volume layer 110-1 returns a “fail” status to thehost and ends method 300.

In step 350, virtual volume layer 110-1 allocates an LD data page tovirtual volume 208 from pool 414 to store data. Step 350 is followed bystep 351.

In step 351, virtual volume layer 110-1 updates the corresponding L3table with a pointer to the new LD data page in virtual volume 208.Specifically, virtual volume 110-1 writes the pointer in the L3 tableentry having an offset identified by the third part of the virtualvolume page address. Step 351 is followed by step 352.

In step 352, virtual volume layer 110-1 writes the data into the new LDdata page at an offset identified by the block offset of the virtualvolume block address. Specifically, virtual volume layer 110-1identifies the block by a logical disk ID and an offset from the startof the logical disk. The offset from the start of the logical disk isdetermined from the sum of (1) the offset of the LD region from thestarting address of the logical disk, (2) the offset of the LD data pagefrom the starting address of the LD region, and (3) the block offset ofthe data block from the starting address of the LD data page. Step 352is followed by step 354.

In step 354, virtual volume 10-1 returns a “pass” status to the host andends method 300.

FIG. 5 illustrates a method 500 for system manager 104 to respond to theevent from a virtual volume layer (e.g., virtual volume layer 110-1) inone embodiment.

In step 502, system manager 104 validates the virtual volume ID andretrieves a data allocation control structure (DC) for the virtualvolume identified by the virtual volume ID. DC, also know as commonprovisioning group (CPG), is a part of system manager 104 that sets themaximum physical allocation for each virtual volume, the maximumphysical allocation of all the virtual volumes owned (i.e., controlled)by the DC, and warning points for the physical allocation of eachvirtual volume and the DC itself. DC also sets the RAID characteristicsof the logical disks and the set of nodes in a cluster from which thephysical disk drive chunklets are allocated when creating additionallogical disks.

In step 504, system manager 104 determines if the physical allocation ofthe identified virtual volume (e.g., virtual volume 208) is over themaximum physical allocation specified by the DC. The maximum physicalallocation can have a default value or be set by the user. If the sizeof the virtual volume is over the maximum physical allocation, step 504is followed by step 528. If not, step 504 is followed by step 508.

In step 508, system manager 104 determines if one or more LD regions areavailable in existing logical disks (e.g., logical disk 207). If one ormore LD regions are available, step 508 is followed by step 514. If not,step 508 is followed by step 510.

In step 510, system manager 104 determines if the total physicalallocation of the virtual volumes owned by the DC is over the maximumphysical allocation specified by the DC. If the size of the DC is overthe maximum physical allocation, step 510 is followed by step 528. Ifnot, step 510 is followed by step 512.

In step 512, system manager 104 instructs logical disk layer 112-1 tocreate one or more new logical disks from chunklets in the physicaldisks. Step 512 is followed by step 513A.

In step 513A, system manager 104 determines if the size of the DC isover a warning point specified by the DC. The warning point provides anearly warning to the user that the physical limit is approaching. Thewarning point can have a default value or be set by the user. If thesize of the DC is over the warning point, step 513A is followed by step513B. If not, step 513A is followed by step 514.

In step 513B, system manager 104 issues an allocation warning alert tothe administrator of system 100. Step 513B is followed by step 514.

In step 514, system manager 104 allocates (e.g., assigns) one or moreavailable LD regions in the logical disk (whether existing or newlycreated) to be mapped to virtual volume pages. Each LD region isidentified by a logical disk ID and an offset from the start of thelogical disk. Step 514 is followed by step 516.

In step 516, system manager 104 determines if the physical allocation ofthe virtual volume is over a warning point specified by the DC. Thewarning point provides an early warning to the user that the physicallimit is approaching. The warning point can have a default value or beset by the user. If the size of the virtual volume is over the warningpoint, step 516 is followed by step 518. If not, step 516 is followed bystep 520.

In step 518, system manager 104 issues an allocation warning alert tothe administrator of system 100. Step 518 is followed by step 520.

In step 520, system manager 104 updates the table of contents (TOC). TOCstores the organization of the virtual volumes, the logical disks, andthe chunklets of server 100 on one or more physical disk drives. Step520 is followed by step 522.

In step 522, system manager 104 delivers the one or more LD regions tovirtual volume layer 110-1. As described above, virtual volume layer110-1 divides the one or more LD regions into LD table or data pages andincrements pool 412 or 414 with these new pages. Step 522 is followed bystep 532.

In step 528, system manager 104 issues an allocation failure alert tothe administrator of system 100. Step 528 is followed by step 532.

In step 532, system manager 104 ends method 500.

FIG. 6 illustrates a method 700 for a virtual volume layer (e.g.,virtual volume layer 1101) and a LD layer (e.g., logical disk layer112-1) to respond to a read request from host 118 in one embodiment.

In step 702, virtual volume layer 110-1 receives from host 118 a readrequest of a data block in a virtual volume (e.g., virtual volume 208).The read request identifies the VV data block by a virtual volume ID anda virtual volume block address.

In step 704, volume layer 110-1 traverses tables 402, 404, and 406 tofind a LD data page corresponding to the virtual volume block address.As described above, if such an LD data page exists, the virtual volumeblock address can be mapped by a pointer identifying a logical disk IDand an offset from the start of the logical disk. Step 704 is followedby step 706.

In step 706, volume layer 110-1 determines if it has found the logicaldisk ID and the offset from the start of the logical disk. If so, step706 is followed by step 710. Otherwise step 706 is followed by step 708.

In step 708, virtual volume layer 110-1 returns all zeros to host 118 inresponse to the read request. In one embodiment, the virtual volume(also referred to as a “Thin Provisioned Virtual Volume” or “TPVV”) isimplemented using snapshot technology as a list of differences(exceptions) from a dummy base volume having all zeros. When a datablock for a read request cannot be found in the virtual volume exceptionlist, virtual volume layer 110-1 will look to the dummy base volume forthe requested data block having the specified virtual volume blockaddress. When searching for the requested data block in the dummy basevolume, virtual volume layer 110-1 will find only zeros and thus returnonly zero data to host 118. For a description of a snapshot implementedas an exception list, please see U.S. patent application Ser. No.10/655,951, entitled “Time-And-Space Efficient Mechanism To CreateVirtual Storage Volume Copies,” U.S. patent application Ser. No.10/655,963, entitled “Efficient And Reliable Virtual Volume Mapping,”and U.S. patent application Ser. No. 10/655,961, entitled “Read/WriteSnapshot,” which are incorporated by reference in their entirety. Step708 is followed by step 714.

In step 710 virtual volume layer 110-1 issues a read command to the datablock identified by the logical ID and the identified offset to logicaldisk layer 112-1. Step 708 is followed by step 712.

In step 712, logical disk layer 112-1 performs a normal read to the datablock identified by the logical disk ID and the identified offset. Step712 is followed by step 714.

In step 714, logical disk layer 112-1 ends method 600.

Various other adaptations and combinations and combinations of featuresof the embodiments disclosed are within the scope of the invention.Numerous embodiments are encompassed by the following claims.

What is claimed is:
 1. A method for writing to a virtual volume mappedto a logical disk, comprising: receiving a request to write a data tothe virtual volume at an address; traversing a first table representingthe virtual volume to find a first pointer at a first offset based on afirst portion of the address, the first pointer leading to one of aplurality of second tables (“said one second table”) also representingthe virtual volume; following the first pointer to said one secondtable; traversing said one second table to find a second pointer at asecond offset based on a second portion of the address, the secondpointer leading to one of a plurality of third tables (“said one thirdtable”); if said one second table does not exist, determining if anumber of available table pages in a first pool is less than a firstthreshold; if the number of available table pages in the first pool isnot less than the first threshold, allocating one table page from thefirst pool to form said one second table; writing the first pointer atthe first offset in the first table.
 2. The method of claim 1, furthercomprising: if the number of available table pages in the first pool isless than the first threshold, requesting additional table pages to beadded to the first pool; determining if the additional table pages havebeen added before timing out; if the additional table pages have beenadded before timing out, allocating one table page from the first poolto form said one second table; writing the first pointer at the firstoffset in the first table; if the additional table pages have not beenadded before timing out, returning a write failure message.
 3. Themethod of claim 2, further comprising: following the second pointer tosaid one third table; traversing said one third table to find a thirdpointer at a third offset based on a third potion of the address, thethird pointer leading to one of a plurality of data pages (“said onedata page”); if said one third table does not exist, determining if thenumber of available table pages in the first pool is less than the firstthreshold; if the number of available table pages in the first pool isnot less than the first threshold, allocating one table page from thefirst pool to form said one third table; writing the second pointer atthe second offset in the second table.
 4. The method of claim 3, furthercomprising: if the number of available table pages in the first pool isless than the first threshold, requesting additional table pages to beadded to the first pool; determining if the additional table pages havebeen added before timing out; if the additional table pages have beenadded before timing out, allocating one table page from the first poolto form said one third table; writing the second pointer at the secondoffset in the second table; if the additional table pages have not beenadded before timing out, returning the write failure message.
 5. Themethod of claim 4, further comprising: following the third pointer tosaid one data page; writing the data to said one data page at a fourthoffset based on a fourth portion of the address and returning a writepass message; if said one data page does not exist, determining if thenumber of available data pages in a second pool is less than a secondthreshold; if the number of available data pages in the second pool isnot less than the second threshold, allocating one data page from thesecond pool to form said one data page; writing the third pointer at thethird offset in the third table; writing the data to said one data pageat the fourth offset and returning the write pass message.
 6. The methodof claim 5, further comprising: if the number of available data pages inthe second pool is less than the second threshold; requesting additionaldata pages to be added to the second pool; determining if the additionaldata pages have been added before timing out; if the additional datapages have been added before timing out, allocating one data page fromthe second pool to form said one data page; writing the third pointer atthe third offset in the third table; writing the data to said one datapage at the fourth offset and returning the write pass message; if theadditional data pages have not been added before timing out, returningthe write failure message.
 7. The method of claim 6, in response to saidrequesting additional table pages to be added to the first pool or saidrequesting additional data pages to be added to the second pool,retrieving an allocation control structure associated with the virtualvolume, the allocation control structure comprising a first maximumphysical allocation for the virtual volume, a second maximum physicalallocation for a group of virtual volumes including the virtual volume,a first warning point on the first maximum physical allocation, a secondwarning point on the second maximum physical allocation, and RAIDparameters controlling the creation of additional logical disk storage;determining if the virtual volume is greater than the first maximumphysical allocation; if the virtual volume is greater than the firstmaximum physical allocation, issuing an allocation failure alert andterminating the allocation request processing.
 8. The method of claim 7,further comprising, if the virtual volume is not greater than the firstmaximum physical allocation, determining if the logical disk has onestorage unit (“logical disk region”) available; if the logical disk hasone logical disk region available, dividing said one logical disk regioninto table or data pages; allocating the table or data pages to thefirst or the second pool; updating a system table of contents to recordthe allocation of said one logical disk region to the virtual volume;determining if the virtual volume is greater than the first warningpoint; if the virtual volume is greater than the first warning point,issuing an allocation warning alert.
 9. The method of claim 8, furthercomprising: if the logical disk does not have one logical disk regionavailable, determining if the group of virtual volumes is greater thanthe second maximum physical allocation; if the group of virtual volumesis greater than the second maximum physical allocation, issuing anallocation failure alert and terminating the allocation requestprocessing.
 10. The method of claim 9, further comprising: if the groupof virtual volumes is not greater than the second maximum physicalallocation, creating a new logical disk; determining if the group ofvirtual volumes is greater than the second warning point; if the groupof virtual volumes is greater than the second warning point, issuing anallocation warning alert; dividing a logical disk region from the newlogical disk into table or data pages; allocating the table or datapages to the first or the second pool; and updating a system table ofcontents to record the allocation of the logical disk region to thevirtual volume.
 11. The method of claim 1, wherein the virtual volume isdistributed amongst a system of nodes, the method further comprisingreplicating the data to another node in the system.
 12. A method forprovisioning a virtual volume mapped to a logical disk, comprising:receiving a request to write a data to the virtual volume at an address;traversing a table representing the virtual volume to find a pointer atan offset based on a portion of the address, the pointer leading to oneof a plurality of data pages (“said one data page”); if said one datapage does not exist, determining if a number of available data pages ina pool is less than a threshold; if the number of available data pagesin the pool is less than the threshold, requesting additional data pagesto be added to the pool; determining if the logical disk has one storageunit (“logical disk region”) available; if the logical disk has onelogical disk region available, dividing said one logical disk regioninto data pages; allocating the data pages to the pool.
 13. The methodof claim 12, further comprising: if the logical disk does not have onelogical disk region available, creating a new logical disk; dividing alogical disk region from the new logical disk into data pages;allocating the data pages to the pool.
 14. The method of claim 13,further comprising: if the number of available data pages in the pool isnot less than the threshold, allocating one data page from the pool toform said one data page; writing the data to said one data page at theoffset based on another portion of the address and returning a writepass message.
 15. The method of claim 12, in response to said requestingadditional data pages to be added to the pool, further comprising:issuing an allocation failure alert if the virtual volume is greaterthan a limit point on maximum physical allocation.
 16. The method ofclaim 15, in response to said requesting additional data pages to beadded to the pool, further comprising: issuing an allocation warningalert if the virtual volume is greater than a warning point on maximumphysical allocation, the warning point being less than the limit point.17. The method of claim 12 in response to said requesting additionaldata pages to be added to the pool, further comprising: issuing anallocation failure alert if a group of virtual volumes is greater than alimit point on maximum physical allocation.
 18. The method of claim 17,in response to said requesting additional data pages to be added to thepool, further comprising: issuing an allocation warning alert if a groupof virtual volumes including the virtual volume is greater than awarning point on maximum physical allocation, the warning point beingless than the limit point.